home *** CD-ROM | disk | FTP | other *** search
- On Tue, 16 Jan 1996, Magnus Kollberg wrote:
-
- > > You can use 320x200 for the status bar. Because the RESOLUTION SET is
- > > 320x200. 160x200 is only a locical concept where you use long to update
- > > graphics instead of word.
- >
- > Okeydokey... this was more complicated than I thought. :-)
- > Can't we use dithering and make it run in a GEM window too? This would be nice
- > and it was possible with the old c-version, DVIEW. ;-)
-
- Okay, short summary:
-
- Smallest allowed resolution on RGB: 288x100
- This is a _true_ resolution in that is works exactly like any other
- resolution. 288 pixels across from edge to edge (no borders)
-
- Smallest resolution on VGA: 288x200
- This is not really true, since we have some small borders on VGA with
- this resolution but it's good because it's the same X resolution as the
- RGB version.
-
- 288x100 on VGA:
- This is simple but looks a bit ugly. Basically we have very big borders
- on the top and bottom of the screen. I use it to be able to use my VGA
- monitor when deleoping RGB 288x100 programs (demos).
- Anyway, apart from the way it looks, this resolution is exactly like
- 288x100 on RGB and takes only a few percent more bus time than on RGB.
-
- 144x100 on RGB:
- When doubling the pixel size (halving the X resolution) you have to do
- more than just change the screen mode. The screen is set to 288x100 (or
- 320x100 or 320x240 or whatever) and you update two pixels at the same
- time. For example, consider a blue pixel in trucolour. It has the value
- 0x001F. If you user douple pixels instead, then the data to be moved in
- order to get a big blue pixel would be: 0x001F001F. Get it?
-
- --
- Elias Martenson
- elias@omicron.se
-
-